It is required that user understands what he is doing. ;)
In different words - everything you are doing, you are doing on your own risk.
Author take no any responsibilities for damaging tuner on other issues.
Thanks to All Duckbox defelopers and especially GOst, nit, schichu, Mira4.

1.Description:
	This doc explains in details how to use specific DuckBA commands and options. If you are not interested in details, skip it and familiarize with pocket consultant doc.

2a.Installation for duckboxes (E2/Neutrino):
	DuckBA uses mtdblock3 partition to exchange files between kernel and uboot. As this partition is in standard image mapped to /boot folder,
	DuckBAS initialisation simply changes configuration of E2/N to free this partition up.
	Steps:
	- Upload DuckBA.tar.gz archive to /tmp folder
	- Start telnet
		- cd /
		- tar -xzf /tmp/DuckBA.tar.gz
		- cd /DuckBA
		- ./DBA.install duckbox
	- Reboot tuner
	- Start telnet
		- cd /DuckBA
		- ./DBA.install duckbox
		- choose Y when asked
	- Reboot tuner
		If all went properly, there should be a file /DuckBA/dba.log written with the content:
			[DBA] Initialise bootmenu
			[DBA] No images found, skipping...
	
2b.Installation for original image:
	- not implemented yet
	
3.Pendrive preparation:
	- use your favorite software (e.g. createmini) to prepare partitions on a pendrive.

4.extract image:
	- Use standard tar command to extract image on a pendrive or....
	- Start telnet
	- cd /DuckBA
	- ./DBA.manage extract <archive name> <device>  [<label>](e.g. ./DBA.manage extract /tmp/BPanther.tar.gz /dev/sda1 BPanther)
			NOTE: It's alwasy good practice to set meaningful label. ;)

5.image preparation:
	- start telnet
	- ./DBA.manage prepare <device> [<device 4 uboot>]
	- where:
		<device> can be: /dev/sd[a-z][1-9]
				 label of the partition
		<device 4 uboot>:/dev/sd[a-z][1-9] - device how uboot sees disk. If you have 1 pendrive it will be most probably sda
			
6. Add new item to bootmenu:
	- cd /DuckBA
	- ./DBA.manage add <itemID [1-3]> <menu item name> <prepared image name>
	- where:
		<itemID> - just number between 1 and 3
		<menu item name> - 16 chars long name which will be displayed on the VFD
		<prepared image name> - filename of the prepared uImage in step 5. Can be found in images directory
		
7. Building multiboot:
	- cd /DuckBA
	- ./DBA.manage build

		8. Remove item from bootmenu:
	- Simply delete specific file in the /DuckBA/images folder

9. Manual image(s) activation:
	- cd /DuckBA
	- ./DBA.manage activate <flash | last | [1-3]>
	- where:
		flash - setting booting from flash
		last - setting booting from last used USB image
		[1-3] setting booting from image 1-3 (look at bootmenu step)

10. Backup of the soft or configuration:
	- cd /DuckBA
	- ./DBA.manage backup <duckba | config>"
	tools description:
	- img2targz.sh bash script to export files from img image to .tar.gz file, has to be run on PC linux
